-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test: refactor setup and get all tests passing #442
Conversation
"host" => host, | ||
"ssl_peer_metadata" => true, | ||
"ssl_certificate_authorities" => [ certificate.ssl_cert ], | ||
"ecs_compatibility" => 'disabled' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't have a test case for tls metadata in ecs mode, isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be elsewhere - recall writing this spec as specifically guarding against a NPE regression,
the bug surfaced regardless of ecs_compatibility
and the test's intention isn't verifying ECS vs non-ECS field behavior (I understand it might seem so on first sight).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change LGTM. Thanks for fixing the CI.
A suggestion is to add a test case for tls metadata in ecs mode.
back to 🟢
harder than expected due LogStash::ConfigurationError: File does not contain valid private key #443
refactored the Dockerfile to use the base file (from .ci) and have the extra
install openssl
in.ci/setup.sh
hook